Skip to content

[Snyk] Fix for 4 vulnerabilities#11567

Closed
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-ac862b96ac600ad5368f24df267dd38d
Closed

[Snyk] Fix for 4 vulnerabilities#11567
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-ac862b96ac600ad5368f24df267dd38d

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Jan 31, 2026

snyk-top-banner

Snyk has created this PR to fix 4 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • plugins/newrelic-dashboard/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Directory Traversal
SNYK-JS-TAR-15032660
  149  
medium severity Directory Traversal
SNYK-JS-TAR-15127355
  127  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-DIFF-14917201
  61  
medium severity Uncontrolled Recursion
SNYK-JS-ESLINT-15102420
  45  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Directory Traversal


EntelligenceAI PR Summary

This PR pins specific Backstage core dependencies to fixed versions in the newrelic-dashboard plugin package configuration.

  • Changed @backstage/core-components from workspace protocol to fixed version 0.8.6
  • Changed @backstage/core-plugin-api from workspace protocol to fixed version 0.1.0
  • Other Backstage dependencies remain on workspace protocol
  • Likely addresses version compatibility requirements or prepares plugin for independent distribution

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Jan 31, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on improving the security posture of the project by resolving identified vulnerabilities within its yarn dependencies. It achieves this by updating specific package versions in the plugins/newrelic-dashboard module, ensuring that the project benefits from the latest security patches.

Highlights

  • Vulnerability Remediation: This pull request, automatically generated by Snyk, addresses four medium-severity security vulnerabilities, including Directory Traversal, Regular Expression Denial of Service (ReDoS), and Uncontrolled Recursion, by updating project dependencies.
  • Dependency Version Pinning: The plugins/newrelic-dashboard/package.json file has been modified to pin the versions of @backstage/core-components to 0.8.6 and @backstage/core-plugin-api to 0.1.0, moving from workspace:^ references to specific versions.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@snyk-io
Copy link
Copy Markdown

snyk-io Bot commented Jan 31, 2026

Snyk checks have failed. 1 issues have been found so far.

Status Scanner Critical High Medium Low Total (1)
Open Source Security 0 0 1 0 1 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request, automatically generated by Snyk, attempts to fix security vulnerabilities by downgrading dependencies. However, the proposed changes in plugins/newrelic-dashboard/package.json are incorrect and will likely break the application. The PR replaces workspace-local dependencies (workspace:^) with pinned, very old versions of @backstage/core-components and @backstage/core-plugin-api. This is a critical issue that goes against the project's monorepo structure and will cause dependency conflicts and build failures. The fact that Snyk failed to update the yarn.lock file, as noted in the PR description, is another strong indicator that these changes are invalid. The changes should be reverted, and the vulnerabilities should be addressed through a proper dependency update strategy, likely by updating packages rather than downgrading them.

Comment on lines +26 to +27
"@backstage/core-components": "0.8.6",
"@backstage/core-plugin-api": "0.1.0",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

These changes introduce a significant downgrade of core Backstage dependencies and remove the workspace:^ protocol. This will almost certainly break the application and goes against the monorepo's dependency management strategy.

  • Version Downgrade: @backstage/core-components is downgraded from a version compatible with 0.13.4-next.0 to 0.8.6. Similarly, @backstage/core-plugin-api is downgraded from 1.5.3 to 0.1.0. Such large downgrades will lead to API incompatibilities and build failures.
  • Workspace Protocol: In a Yarn workspace-based monorepo, internal packages should reference each other using workspace:^. This ensures that the versions are consistent across the entire project. Removing this will lead to dependency resolution issues and potentially multiple versions of the same package being installed.

These changes should be reverted. The underlying security vulnerabilities should be addressed by updating dependencies, not by this drastic downgrade.

    "@backstage/core-components": "workspace:^",
    "@backstage/core-plugin-api": "workspace:^"

@entelligence-ai-pr-reviews
Copy link
Copy Markdown

Walkthrough

This PR modifies the dependency management strategy for the newrelic-dashboard plugin by pinning two Backstage core packages to specific versions instead of using the workspace protocol. The @backstage/core-components package is now locked to version 0.8.6 and @backstage/core-plugin-api to version 0.1.0. Other Backstage dependencies continue to use the workspace protocol. This change suggests preparation for standalone plugin distribution or resolution of version compatibility constraints that require these specific package versions.

Changes

File(s) Summary
plugins/newrelic-dashboard/package.json Pinned @backstage/core-components to version 0.8.6 and @backstage/core-plugin-api to version 0.1.0, replacing workspace protocol with fixed versions.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant NRD as NewRelic Dashboard Plugin
    participant CC as @backstage/core-components
    participant CPA as @backstage/core-plugin-api

    Dev->>PM: Run package install
    PM->>NRD: Read package.json dependencies
    
    Note over NRD,CPA: Dependency Version Change
    
    alt Before (workspace reference)
        NRD->>PM: Request @backstage/core-components@workspace:^
        PM->>CC: Resolve from local workspace
        NRD->>PM: Request @backstage/core-plugin-api@workspace:^
        PM->>CPA: Resolve from local workspace
    else After (pinned versions)
        NRD->>PM: Request @backstage/core-components@0.8.6
        PM->>CC: Resolve specific version 0.8.6
        NRD->>PM: Request @backstage/core-plugin-api@0.1.0
        PM->>CPA: Resolve specific version 0.1.0
    end
    
    PM-->>NRD: Dependencies installed
    PM-->>Dev: Installation complete
    
    Note over NRD: Plugin now uses pinned versions<br/>instead of workspace references
Loading

▶️AI Code Reviews for VS Code, Cursor, Windsurf
Install the extension

Note for Windsurf Please change the default marketplace provider to the following in the windsurf settings:

Marketplace Extension Gallery Service URL: https://marketplace.visualstudio.com/_apis/public/gallery

Marketplace Gallery Item URL: https://marketplace.visualstudio.com/items

Entelligence.ai can learn from your feedback. Simply add 👍 / 👎 emojis to teach it your preferences. More shortcuts below

Emoji Descriptions:

  • ⚠️ Potential Issue - May require further investigation.
  • 🔒 Security Vulnerability - Fix to ensure system safety.
  • 💻 Code Improvement - Suggestions to enhance code quality.
  • 🔨 Refactor Suggestion - Recommendations for restructuring code.
  • ℹ️ Others - General comments and information.

Interact with the Bot:

  • Send a message or request using the format:
    @entelligenceai + *your message*
Example: @entelligenceai Can you suggest improvements for this code?
  • Help the Bot learn by providing feedback on its responses.
    @entelligenceai + *feedback*
Example: @entelligenceai Do not comment on `save_auth` function !

Also you can trigger various commands with the bot by doing
@entelligenceai command

The current supported commands are

  1. config - shows the current config
  2. retrigger_review - retriggers the review

More commands to be added soon.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Feb 7, 2026

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

@github-actions github-actions Bot added the stale label Feb 7, 2026
@github-actions github-actions Bot closed this Mar 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants